Service Domain Charging Systems and Methods

ABSTRACT

Various mechanisms are disclosed for a service domain charging system that can interact with underlying networks. A service domain charging architecture is defined with several logical functions. Service-based charging types may be and applied to existing event, session, online, and offline charging mechanisms. Service domain charging messages may be exchanged over the X, Y, Z reference points. An E reference point may be used for interfacing with a service domain billing system, and a B reference point may be used between a service domain billing system and underlying network&#39;s billing system.

CROSS REFERENCE TO RELATED APPLICATIONS

This application is a continuation of U.S. patent application Ser. No.14/339,899 “Service Domain Charging Systems and Methods” filed Jul. 24,2014 which claims the benefit of, and incorporates herein by reference,U.S. Provisional Application 61/886,458 “Service Domain Charging Systemand Interactions with Underlying Networks” filed Oct. 3, 2013 and U.S.Provisional Application 61/857,912 “Service Domain Charging System andInteractions with Underlying Networks” filed Jul. 24, 2013. Thedisclosures of each application listed in this paragraph are herebyincorporated by reference as if set forth in their entireties herein.

BACKGROUND

Machine-to-machine (M2M) technologies allow devices to communicate moredirectly with each other using wired and wireless communicationssystems. M2M technologies enable further realization of the Internet ofThings (IoT), a system of uniquely identifiable objects and virtualrepresentations of such objects that communicate over a network, such asthe Internet. IoT may facilitate communication with even mundaneeveryday objects, such as products in a grocery store, and therebyreduce costs and waste by improving knowledge of such objects. Forexample, stores may maintain very precise inventory data by being ableto communicate with, or obtain data from, objects that may be ininventory or may have been sold. M2M technologies introduce newchallenges in charging for services, such as determining who can chargefor services, who should be charged for such services, and whatoperations are chargeable.

SUMMARY

Disclosed herein are methods, devices, and systems related to a servicedomain charging system that can interact with underlying networks. Aservice domain charging architecture may include several logicalfunctions, including a Service Domain Charging Management (SD-CM), aService Domain Online Charging System (SD-OCS), a Service Domain OfflineCharging System (SD-OFCS), and a Service Domain Charging TriggerFunction (SD-CTF). Service-based charging types may be created andapplied to existing event, session, online, and offline chargingmechanisms. Service domain charging messages may be exchanged over theX, Y, Z reference points. An E reference point may be used forinterfacing with a service domain billing system, and a B referencepoint may be used between a service domain billing system and theunderlying network's billing system.

One embodiment is a method including receiving a policy at a servicedomain charging management function in a service layer of an M2Mnetwork. This policy is defined as a rule with associated attributes.The method also includes using the policy to determine chargeable eventswithin the service layer of the M2M network.

An exemplary charging system for an M2M service domain can include aservice domain charging management function to store charging policiesfor the service domain; a service domain on-line charging systemreceiving service requests from the service domain charging managementfunction and checking the credit for the requested service beforegranting the service; and a service domain off-line charging systemreceiving charging events from the service domain charging managementfunction and producing service domain charging data records.

One embodiment is a method including receiving at a service domaincharging management function at an infrastructure node charging policiesfor the service domain. The method can include distributing the policiesfrom the service domain charging management function at theinfrastructure node to a service domain charging management function atan end node.

One embodiment is a method including transferring charging informationbetween a service domain charging system in the service layer and aMachine-Type Communications Interworking Function (MTC-IWF) in a 3GPPnetwork across a Tsp reference point. The method also includes using thetransferred charging information in the service domain charging systemin the service layer or the MTC-IWF in the 3GPP network.

This Summary is provided to introduce a selection of concepts in asimplified form that are further described below in the DetailedDescription. This Summary is not intended to identify key features oressential features of the claimed subject matter, nor is it intended tobe used to limit the scope of the claimed subject matter. Furthermore,the claimed subject matter is not limited to limitations that solve anyor all disadvantages noted in any part of this disclosure.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 is a diagram that illustrates an exemplary, non-limiting chargingarchitecture according to an embodiment.

FIG. 2 is a diagram that illustrates an exemplary 3GPP PCC system withOnline charging and Offline charging.

FIG. 3 is a diagram that illustrates another exemplary, non-limitingarchitecture having exemplary MTC-IWF interfaces with a 3GPP Offlinecharging system using the Rf/Ga reference points

FIG. 4 is a diagram that illustrates exemplary, non-limiting, oneM2Marchitecture.

FIG. 5 is a diagram that illustrates an exemplary, non-limiting, ServiceDomain Charging System (SD-CS) including the locations of some exemplarylogical functions and exemplary scenarios for deployment.

FIG. 6A is a flow chart that illustrates an exemplary charging policyconfiguration procedure.

FIG. 6B is a flow chart that illustrates an exemplary charging policyconfiguration procedure in which an application provides the chargingpolicy to the SD-CM.

FIG. 7 is a flow chart that illustrates an exemplary service domainoffline charging procedure.

FIGS. 8A and 8B are a flow chart that illustrates exemplary proceduresfor online charging, including procedures for a credit request and acredit reservation.

FIG. 9 is a flow chart that illustrates exemplary procedures for servicebased charging.

FIG. 10 is a diagram that shows an exemplary non-limiting collection ofcharging rules.

FIG. 11 is a diagram that illustrates an exemplary non-limiting resourcestructure for a <chargingRule> resource.

FIG. 12 is a diagram that illustrates an exemplary non-limiting resourcestructure for <chargingCredit>.

FIG. 13 is a diagram that illustrates an exemplary non-limiting resourcestructure for a charging configuration.

FIG. 14 is a diagram that illustrates an exemplary non-limiting resourcestructure for a <chargeableEvent>.

FIG. 15 is a diagram that illustrates an exemplary non-limiting resourcestructure for a <chargeableService>.

FIG. 16 is a diagram that illustrates an exemplary non-limiting resourcestructure for a <serviceProcedure>.

FIG. 17 is a diagram that illustrates a service domain charging system(SD-CS) that may interface, with an underlying 3GPP network via the Zreference point.

FIGS. 18A and 18B are a flow chart that illustrates a call flow forservice domain interworking with 3GPP on charging related operations forthe device triggering procedure

FIGS. 19A and 19B are a flow chart that illustrates an exemplary signalflow showing the interactions between SD-CS and the 3GPP chargingsystem.

FIG. 20 is a diagram that illustrates an exemplary, non-limitingarchitecture where the SD-CS resides in the Compensation Brokerage (CB)service capability.

FIG. 21 illustrates an exemplary, non-limiting architecture according toan embodiment.

FIG. 22A is a system diagram of an example machine-to-machine (M2M) orInternet of Things (IoT) communication system in which one or moredisclosed embodiments may be implemented.

FIG. 22B is a system diagram of an example architecture that may be usedwithin the M2M/IoT communications system illustrated in FIG. 22A.

FIG. 22C is a system diagram of an example M2M/IoT terminal or gatewaydevice that may be used within the communications system illustrated inFIG. 22A.

FIG. 22D is a block diagram of an example computing system in whichaspects of the communication system of FIG. 22A may be embodied.

FIGS. 23A-23C are diagrams that illustrate exemplary interfaces that canbe used with embodiments.

DETAILED DESCRIPTION OF ILLUSTRATIVE EMBODIMENTS

The European Telecommunications Standards Institute (ETSI) architecturedefines an offline charging system for M2M technologies. In someembodiment integrating aspects of this architecture, charginginformation, in the form of Charging Data Records (CDRs), may be derivedfrom recorded information and transferred to a Charging Server. Allinformation required for charging may first be selected for recording.There may be a one to one mapping between a recorded M2M event and aCDR.

FIG. 1 is a diagram that illustrates an exemplary, non-limiting chargingarchitecture 100 according to an embodiment. In such an embodiment, theCharging Function (CF) 102 embedded within the M2M Network ServiceCapability Layer (NSCL) 104 may be responsible for interaction with theCharging Server 106 using the Cm reference point. Diameter may be usedas the protocol for the Cm reference point.

FIG. 2 is a diagram that illustrates an exemplary 3GPP PCC system 200with Online charging 202 and Offline charging 204 as well as otherinvolved entities. A 3rd Generation Partnership Project (3GPP) Policyand Charging Control (PCC) system may be responsible for Quality ofService (QoS) and charging for IP Connectivity Access Networks (IP-CANs)(e.g., EPS, UMTS, fixed, I-WLAN, etc.). The PCC architecture may includea number of functions with specified interfaces between them. The Policyand Charging Rules Function (PCRF) 206 may be responsible for creatingPolicy and Charging related information for IP-CAN sessions, IP-CANbearers, and/or Service Data Flows (SDFs). 3GPP may support both Offlinecharging 204 and Online charging 202. Offline charging 204 is amechanism where charging information does not affect, in real-time, theservice rendered, such as post-paid subscribers. On the contrary, theOnline Charging System (OCS) 202 performs charging functions, such asCredit Control, in real-time. This allows the OCS 202 to affect serviceexecution in real-time, typically for pre-paid subscribers. Variouscharging models are supported in 3GPP, including volume-based charging,time-based charging, combined volume- and time-based charging,event-based charging, and no charging.

FIG. 3 is a diagram that illustrates another exemplary, non-limitingarchitecture 300 having exemplary MTC-IWF interfaces with a 3GPP Offlinecharging system using the Rf/Ga reference points. The MTC-IWF (MachineType Communications-InterWorking Function) entity 302 interfaces a M2Mservice capability server 304. Tsp may provide the control planeinterface and Gi/SGi may be the user plane interface.

FIG. 4 is a diagram that illustrates an exemplary, non-limiting, oneM2Marchitecture 400. oneM2M is a recently proposed standard at an earlystage of architecture design. A central part of oneM2M is a CommonService Entity (CSE) that consists of multiple Common Service Functions(CSFs) 402. A CSF 402 in a CSE may be a service such as Registration,Security, Charging, data management, etc. A CSE may reside in M2M endnodes (e.g., devices), intermediate nodes (e.g., gateways), andinfrastructure nodes (e.g., network platforms). oneM2M defines threereference points, an X reference point between Applications and CSE, a Yreference point between two CSEs, and a Z reference point between CSEand the underlying networks. oneM2M has updated the reference pointnames from X, Y and Z to the Mca, Mcc and Mcn. The operations apply tothe Mcc reference point also apply to the Mcc′ reference point, which isbetween inter service provider domains. Some exemplary oneM2M chargingrequirements are illustrated below in Table 1.

TABLE 1 Exemplary oneM2M Requirements for Charging Requirement IDDescription CHG-001 The M2M system shall support collection of chargingspecific information related to the individual services facilitated bythe system (e.g. Data Management, Device Management and/or Connectivitymanagement), and concurrently with the resource usage. The format of therecorded information shall be fully specified including mandatory andoptional elements. CHG-002 The M2M system shall support mechanism tofacilitate correlation (e.g. subscriber identity) of charginginformation collected for different services, including those providedby the underlying network operator CHG-003 The M2M system shall be ableto reuse existing charging mechanisms of underlying networks. CHG-004The M2M system shall support transfer of the charging informationrecords to the Billing Domain of the M2M Service Provider, for thepurpose of subscriber billing, inter-provider billing, and/orprovider-to-subscriber accounting including additional functions likestatistics. CHG-005 The M2M system should support generation of chargingevents for the purpose of requesting resource usage authorization fromthe real time credit control system where the subscriber account islocated. The information contained in the charging events and therelevant chargeable events shall be fully specified including mandatoryand optional elements. A chargeable event may be any activity a providermay want to charge for that utilizes the resources and related M2Mservices offered by such provider. A charging event is the set ofcharging information needed by the credit control system for resourceauthorization.

In the M2M service domain, which, as used herein, refers to M2M servicesprovided by an M2M service provider, including the Service CapabilityLayer (SCL) of the ETSI M2M architecture and the CSE and CSF of a oneM2Marchitecture, new challenges are presented for charging, as there aremore complex stakeholders and new charging scenarios in suchembodiments. Table 2 below lists some exemplary charging scenarios atthe service domain, each of which may be combined with others (shown inTable 2 or otherwise).

TABLE 2 Exemplary Service Domain Charging Scenarios and StakeholdersChargeable Entities to Entities being Charging Events/OperationsDescription charge charged schemes Subscription Charging is based oneach Service A service Most likely fix M2M service domain Providersubscriber can rate, e.g. subscription. The M2M be a CSE or monthly feeService Provider charges the an application. M2M service subscriber. Ithas a unique service subscriber ID. Service connection Servicesubscribers are Service Service The rate is charged per secure serviceProvider subscriber determined per connection. One subscriber servicecan have multiple service connection; by connections. connectionduration. Charging event is finished when the service connection tearsdown Service Charging is based on Service The entity that The rate isRegistration service domain registrations Provider registers todetermined per the service registration domain, e.g. an Application orCSE or CSF Data Operations Charging is based on basic 1) Owner of 1)receiver of Owner of the operations on data, such as the data the datadata can charge creation, update, retrieval, 2) both 2) owner of the theentity that deletion, usage of storage owner of data uses the data;space, etc. For example, an the data owner of the Application A writesdata to and the data can be a service domain, and got service charged bythe charged by the service provider service provider provider. Whenapplication B 3) service for data storage reads the data it getsprovider and sharing charged by Application A (or services by bothApplication A and the Service Provider) Service Based Charging is basedon a 1) Service Entity that The rate is Operations service, thus it cancontain a Provider request the determined per series of operations to 2)Owner service, such service achieve the service. For of the data as anexample, Application A application, a requests certain data from a CSE.service provider. The service provider performs a series of actions toread and gather the data for Application A. The service provider ischarged by the owner of the data, and the service provider chargesApplication A for the service.

The service domain may use the following functions to support charging:

-   -   Efficient mechanisms and interfaces to enable service domain        charging that may be self-sufficient and that may be independent        of underlying networks    -   Mechanisms and interfaces that enable the service domain to        interact with and re-use the underlying network charging system        when converged charging is desired    -   Service domain charging mechanisms to support online, offline,        and new charging types that may be used by the service domain

The above functions may not be sufficiently addressed by existingcharging systems. A 3GPP charging system may not address such functionsand may not be applicable to service domain charging. ETSI M2M chargingmay only provide limited charging functions. ETSI M2M defines simpleinformation recording at the network service capability layer and onlyaddresses offline charging. It does not provide any mechanisms forcharging policy control. ETSI M2M also may not define a mechanism tore-use 3GPP charging. Therefore, ETSI M2M charging is very basic and maynot meet the requirements of a complete M2M charging system. oneM2M, asa new standard under development, has not yet defined any chargingfunctions and procedures.

Therefore, according to the embodiments set forth herein, mechanisms maybe used for a service domain charging system that may interact with oneor more underlying networks. More specifically, embodiments aredescribed herein that provide for an overall service domain chargingarchitecture, defining logical functions (e.g., SD-CM, SD-OCS, SD-OFCSand SD-CTF), their functionalities, and their relationships. Embodimentsare also described herein that define a service based charging type andthat apply existing event, session, online, and/or offline charging inthe context of service domain. Embodiments are also described hereinthat define service domain charging messages over the X, Y, Z referencepoints. Furthermore, the current disclosure describes an E referencepoint for interfacing with a service domain billing system and a Breference point between the service domain billing system and anunderlying network's billing system. The current disclosure also setsforth an architecture, messages, and interactions with the 3GPP chargingsystem. Embodiments are further set forth for ETSI M2M charging. Definedresource (i.e., data) structure and procedures supporting the disclosedmechanisms are also set forth herein. Note that while the terms usedherein may be associated with the oneM2M architecture, standards, andrelated documents, the presently disclosed embodiments may be applied toany service domain charging system.

Various charging types may be supported at the service domain in theembodiments described herein. Each may support the possible chargingscenarios described above in Table 2. The terms used in 3GPP chargingmay be used herein for simplicity, such as Online/Offline charging, withthe functionalities expanded according to the described embodiments toprovide more flexibility in the service domain for new chargingscenarios. A service based charging type is set forth herein to satisfyservice domain requirements.

In addition to the traditional session-based and event-based charging,the service domain may provide unique service-based charging. Since aCSE may contain many different CSFs, and it may also manage “big” data,a CSE may perform a complex request that involves a series of actions,multiple inputs, and multiple decisions. Such a request may result inthe requestor being charged by the service rather than for one or moresteps of an operation.

A service domain may have its own sessions or may be session-less. Inthe context of charging, the term “session” as used herein has a broadscope. A service session may be a subscriber's subscription to aspecific service provider and/or it may be a logical service connection.A subscriber may have multiple service connections. For example, aservice registration may be in process, such as when a CSE in an endnode registers to a CSE in an infrastructure node. Such registration maybe considered a session and charging may be done per registration. Asession may be identified by a unique service session identifier (ID)and may be associated with a subscriber ID, a session duration, aservice session QoS, and/or other information that may affect charging.

Service Domain Events may refer to non-continuous transactions, such asan operation on data (e.g., Create, Update, Retrieval, etc.).

Service domain charging methods may be divided into Online and Offlinecharging, in some embodiments based on how charging affects real timeservices, similar to the concepts of Online and Offline charging in3GPP. Offline charging may not affect services provided in real time.Charging triggering information may be generated at the CSFs where ithappens. A charging report with Offline charging data may be passed viadifferent nodes to the network to generate Service Domain CDRs(SD-CDRs). Online charging may affect services granted in real time. Aservice request may first be generated and the requestor's credit may bechecked before the service is granted. Whether a service uses Online orOffline charging may be based on service sessions or events. Forexample, an application may create data in the service domain andspecify that reading the data is event-based Online charging with acertain rate. A subscriber (e.g., a user, an application) may be chargedby using a combination of both Online and Offline charging mechanisms.

The Service Domain Charging System (SD-CS) may consist of four logicalfunctions. FIG. 5 is a diagram that illustrates an exemplary,non-limiting, Service Domain Charging System (SD-CS) including thelocations of some exemplary logical functions and exemplary scenariosfor deployment. The dotted lines of architecture 500 indicate optionalfunctions in the node. Architecture 500 may support both a centralizedcharging system with control at the infrastructure node and adistributed charging system with control over different nodes. Describedbelow are features of the functions and call flows and messages forcharging.

The Service Domain Charging Management (SD-CM) 502 may be central toSD-CS. The SD-CM 502 may contain charging policies that the CSE 506supports. It may obtain charging policies by provisioning and/orconfiguration. The policies may be obtained from the service provider orthey may be configured by an application 508 or another CSE 510. TheSD-CM 502 may also update its policy based on statistics of chargeableevents at the service layer. The SD-CM 502 may have internal interfaceswith other CSFs in the same CSE 506. The SD-CM 502 may configure otherCSFs 504 regarding chargeable events and policies.

The SD-CM 502 may serve as the aggregator and dispatcher of charginginformation. It may receive charging requests and events from other CSFs504. The SD-CM 502 may dispatch the requests to either Service DomainOnline Charging System (SD-OCS) 512 or the Service Domain OfflineCharging System (SD-OFCS) 514. The SD-CM 502 may get output from theSD-OCS 512 and/or the SD-OFCS 514 and may send the information to eitherthe Service Billing Domain or an underlying network's charging system,based on the policy. The SD-CM 502 may be the anchor point forinteractions among the SD-CS in different nodes (such as infrastructurenodes, intermediate nodes, and end nodes). The SD-CM 502 may also be theanchor point for the SD-CS to interface and interact with an underlyingnetwork for charging related operations.

The Service Domain Offline Charging System (SD-OFCS) 514 may receiveoffline charging events from a SD-CM 502 and generate SD-CDRs and SD-CDRfiles. The Service Domain Online Charging System (SD-OCS) 512 mayreceive service requests, check credit, and grant services. The SD-OCS512 can maintain the credit information for different entities.

An intermediate node or an end node may or may not have one or both ofthe SD-OFCS 514 and the SD-OCS 512 depending on the deployment. TheSD-CM 502 in the infrastructure node may configure the SD-CM 518,SD-OFCS 520, and SD-OCS 522 in the intermediate node 510 and the SD-CM524, SD-OFCS 526, and SD-OCS 528 in the end node 527 so charging can bedone locally in order to reduce traffic between the nodes and increaseresponse time.

One or more Service Domain Charging Trigger Function (SD-CTF) 530, 532,and 534 may reside in the CSFs as shown in the small boxes of FIG. 5.Some CSFs may not have a SD-CTF function. SD-CM 502 may configure theSD-CTF 530 regarding chargeable events and how to report.

The SD-CS 502 may advertise its charging related information, such asrate, to other CSEs or applications via the Y or X referent point. TheSD-CS 502 may utilize the charging and billing system in the underlyingnetworks via the Z reference point. Internal to the SD-CS, the SD-OCS512 and SD-OFCS 514 may communicate with each other. Further detailsabout such embodiments are provided herein.

The service domain may have its own billing system 536. The SD-CS in theinfrastructure node 506 may communicate with the service domain billingsystem 536 via a reference point referred to as E. The E referent pointconnects the M2M service domain (e.g., CSEs) to external lateral systemsthat are not applications or underlying networks. The billing domain maybe a third party application, such as PAYPAL. The service domain mayexchange charging and billing information with the billing domain viathe E reference point. The service domain billing system 536 may alsohave a B reference point with the billing system 540 in the underlyingsystem since they may come from different providers.

When there is no SD-CM in an end node 527, the SD-CM 518 in theintermediate node 510 or SD-CM 502 in the infrastructure node 527 wherethe end node registers may act as a proxy and aggregator for charging.Such a SD-CM 518 in the intermediate node 510 or a SD-CM 502 in theinfrastructure node 527 may collect charging events and store and applycharging policies for the end nodes. In some cases there is no SD-CTF inthe end node 527 as well. The transactions and charging related to theend node 527 may be captured at the intermediate node 510 orinfrastructure node 506.

Illustrated in the figures are operations by the SD-CS at theinfrastructure node 506 and the end node 527. The same concepts andprocedures apply to the intermediate nodes 510. Multi-hop chargingoperations are possible, for example where the SD-CS in theinfrastructure node 506, intermediate node 510, and end node 527communicate with each other. While the figures show that the chargingevents may occur at the end node 527, charging events may also occur atthe intermediate node 510 or the infrastructure node 506. If they occurat the infrastructure node 506, the SD-CS at the infrastructure node mayprocess the charging information. The SD-CS may choose to push thecharging information to the intermediate node 510 or the end node 527for sharing of information.

FIG. 6A is a flow chart that illustrates exemplary charging policyconfiguration procedure 600. Note that the flow indicates one possiblecommon scenario when the SD-CM 502 in the infrastructure node 506obtains charging policies and configures the charging functions in otherregistered CSEs 510 and 527. Other scenarios not shown that may besupported by various embodiments include where an application 508 mayprovide its own specific charging policy to an SD-CM 502 via the Xreference point. Such a policy may be exchanged and configured betweenthe CSEs in different nodes. The CSEs may also facilitate theadvertising and exchange of policies between different applications. Forexample, an M2M app in an app store may use the X reference point topush its own charging policy or it may query an existing charging policyon a service domain. The app may be an entity to collect the charge.Another scenario not shown that may be supported by various embodimentsmay be where a charging policy may also be initiated and populated froman intermediate node 510 and an end node 527, and verified andaggregated by the SD-CM 502 in the infrastructure node 506. Yet anotherscenario not shown that may be supported by various embodiments may bewhere a charging policy may be updated dynamically over time. Forexample, a change of rates, chargeable events, etc. may be updated. Suchupdates can be initiated by applications or CSEs at different nodes.

FIG. 6B is a flow chart that illustrates an exemplary charging policyconfiguration procedure in which an application provides the chargingpolicy to the SD-CM. SD-CM can provide the charging policy establishedby one application to other applications. The application thatconfigures the charging policy can collect chargeable events and chargeother applications via service domain. If authorized, the SD-CM candistribute the charging policies to other nodes.

Examples of charging policies include supported charging types (e.g.,Online, Offline, Service Based), association of subscriber ID andapplication/subscriber types with charging types (e.g., Online, Offline,Service Based), association of subscriber ID, application/subscribertypes, and service domain operations with rate, a list of chargeableevents, chargeable event reporting parameters, and credit reservationtrigger and threshold.

FIG. 7 is a flow chart that illustrates exemplary service domain offlinecharging procedure 700, where, in the shown embodiment, it is assumedthat there is no SD-OFCS at the end node. When a chargeable eventhappens, the SD-CTF 534 at the CSF 542 reports the event. The SD-CM 524at the end node 527 may aggregate these reports before sending them tothe infrastructure node 506.

FIGS. 8A and 8B are a flow chart that illustrates exemplary procedures800 (not necessarily shown in sequential order) for online charging,including procedures for a credit request and a credit reservation. InOnline charging embodiments, a requestor (e.g., an application, asubscriber, a CSE, etc.) must have enough credit to pay for a servicebefore the service is granted. If there is not enough credit, therequest may be denied. The charging related information may be providedin the rejection message, such as lack of credit and charging rate. Thisrejection may trigger other actions at the service domain, such asstarting the credit reservation action or negotiating a new rate usingcharging configuration messages. The requestor may also reserve creditbefore service requests, for example, by requesting the reservation ofenough credit to pay for a retrieval operation of certain data for 20times.

Note that FIG. 8 only illustrates one possible scenario when there is noSD-OCS at the end node 527. When there is SD-OCS 528 at the end node527, the SD-OCS 512 at the infrastructure node may push creditinformation and decision making for specific requestors to the SD-OCS528 at the end node 527 using a Charging Config message. Thus theprocedure of such an embodiment is more distributed and localized at theend node 527. The SD-OCS 528 at the end node or the intermediate node510 may send one or more reports to the SD-OCS 510 at the infrastructurenode 506 using the Charging Report message so that they may synchronizecredit information.

FIG. 9 is flow chart that illustrates exemplary procedures 900 forservice based charging. The steps illustrated are reduced in detail forsimplicity since the messages are described elsewhere herein. At step 1,a service request arrives at the CSE. A “CSF Dispatcher 902” may be usedto represent an entity that processes the requests and identifies thatthe request is targeting a service that involves multiple steps ofoperations. Refer to Table 2 for more descriptions of service basedoperations. At step 2, the CSF Dispatcher 902 distributes the requeststo relevant CSFs. Note that some operations may depend on the responseto other requests, but this is not shown in the figure for clarity.

At step 3, some of the operations to fulfill the service may becompleted. Note that some operations may depend on a credit check beingexecuted. At step 4, the SD-CTF 534 at the CSFs 542 may trigger eithercharging events for Offline charging or a charging request for Onlinecharging. A service request may involve both Online Charging and OfflineCharging. At steps 5, 6, and 7, the SD-CM 524 at the end node 527 maydispatch the service requests for Online charging and charging reportsfor Offline charging to the respective SD-OCS 512 and SD-OFCS 514 at theinfrastructure node 506. It may also aggregate requests and responses.Some of the procedures may be dependent on others. At step 8, otheroperations completed. The CSF Dispatcher 902 may receive a status. Itmay also notify the service requestor of the completion of the service.

Table 3 below lists messages that may be used in the service domaincharging operations. Key information elements (IEs) are listed toindicate the use of these messages, and other IEs may be included toconvey additional information. These messages may be supported bydifferent styles protocols, such as RESTful protocols or basedprotocols, or other protocols based thereon. A service layer chargingsystem as set forth herein may apply a RESTful architecture or anon-RESTful architecture.

TABLE 3 Exemplary Service Domain Charging Operations Messages RelatedResources and Message Name Descriptions Key IEs Reference PointOperations Charging Config The pair of The charging X, Y, Z, E For thesetting of Req/Rsp messages used for policy or a pointer chargingpushing, soliciting to the charging configuration and and negotiatingpolicy, such as an policies, it is charging policies URL of where it isachieved by (such as supported stored; operations (such charging types,Unique IDs to as CREATE, rate, etc). The identify what the RETRIEVE,issuer may send policy applies for, UPDATE, the charging such as aDELETE) of the policies to the subscriber, an chargingConfigs receiver,or it may application, a collection, request charging service, asession, <chargingConfig> policy input from etc. resource or any of thereceiver, the child resource of <chargingConfig>. For the setting ofspecific charging rules, it is achieved by operations on thechargingRules collection, or <chargingRule> for a specific rule, or anattribute of a <chargingRule> resource. Charging Report The pair ofCharging event Y, Z, E chargingRecords Req/Rsp messages used for withits associated are used for the two charging parameters; report.functions to unique IDs of the exchange charging involved entities.information, including service domain offline charging to reportcharging events; SD-OCS at the end node or intermediate node to reportonline charging events to SD-OCS at the infrastructure node Credit CheckThe pair of Credit unit; Y, E Credit check can Req/Rsp messages used fornumber of credits; be achieved by credit checking, unique IDs of theoperating the requesting and involved entities <chargingCredit>granting. resource. Credit Reservation The pair of Credit unit; Y, ECredit reservation Req/Rsp messages used for number of credits; can beachieved a requestor to unique IDs of the by operating the reservecredits from involved entities <chargingCredit> the charging resource.system Billing Req/Rsp The pair of SD-CDR files; E chargingRecordsmessages used for SD-CDRs are used for the the SD-CS to report. exchangebilling information with the service billing domain

In an embodiment, data structures may be used to support the chargingmechanisms disclosed herein. Such data structures may take the form ofresources. A resource may be a uniquely addressable object in theRESTful architecture. A resource may have a representation that can betransferred and manipulated with the RESTful verbs (e.g., CREATE,RETRIEVE, UPDATE, DELETE). A resource may be addressed uniquely using aUniversal Resource Identifier (URI). A child resource may be a resourcethat has a containment relationship with an addressed (i.e., parent)resource. The parent resource representation may contain one or morereferences to sub-resources(s) (i.e., child resources). The lifetime ofa child-resource may be limited by the parent's resource lifetime. Anattribute may store information, such as meta-data about the resourceitself.

Resource-based data structure may make it easier to perform RESTfuloperations, such as using protocols such as Hypertext Transfer Protocol(HTTP) or Constrained Application Protocol (CoAP). However, such a datastructure may also be applied to non-RESTful protocols. A resource maycontain child resource(s) and attribute(s).

The defined structure enables flexible and extensible service layercharging mechanisms. The originator may set up charging policies andconfigurations to the receiver using the chargeConfig resource.Additionally, the originator may set up different charging rules basedon the charging configuration and policies. These rules may indicate who(the entity that charges) will charge whom (the entity being charged)based on what (e.g., online or offline charging, event based, servicebased, or session based charging, etc.). The charging rule enables thesystem to have different granularities. For example, the charging rulemay be based on a logical function, such as a CSE node or anapplication. The charging rule may also or instead, be based on aresource. For example, the charging rule may be based on an entity thatwants to charge every reading operation of a specific resource. Thoughnot shown in the figures, all the resources should support vendorspecific attributes/child resources.

As used in the figures, the following shapes illustrate an exemplary,non-limiting resource structure:

-   -   Square boxes are used for resources and child resources    -   Square boxes with round corners are used for attribute    -   Parallelograms are used for collection of resources

In Read/Write access mode, the following values may be assumed:

-   -   Read/Write (RW) may be set by a CREATE or an UPDATE operation    -   Read Only (RO) may be set by the CSE when the resource is        Created and/or Updated; such an attribute may only be read    -   Write Once (WO) may be set by the requestor (i.e., the entity        that initiated the request) at a Create operation; such an        attribute may thereafter only be read

FIG. 10 is a diagram that shows exemplary non-limiting collection 1000of charging rules 1002 (i.e., charging policies). An application, suchas the SD-CM at a CSE, or another policy server (for example, a thirdparty policy server) may send Charging Config messages to create andupdate charging rules. A collection may have from zero to multipleindividual charging rules, indicated as <chargingRule> 1004. Note that“ID” as used herein may refer to a unique identifier or may be a URIpointing to a location of a referred resource. By referring to IDs,different resources may be effectively associated.

FIG. 11 is a diagram that illustrates exemplary non-limiting resourcestructure 1100 for a <chargingRule> resource. “Common attributes” 1102refers to generic (i.e., non-charging specific) attributes such as thecreation time of a resource and the expiration time of a resource. Thecommon resources that are not specifically associated with charging,such as access right and subscriptions may also be included in “commonattributes”. Note that the <chargingCredit> 1104 may be associated withthis the charging rule or it can be a separate resource. In anembodiment, it may be associated with the entity that has the credit. Ifit is associated with the charging rule, the <chargingCredit> 1104 maydefine the receiver's credit. If it is a separated resource, it mayeither include an entity ID to associate to an entity, or its parentresource needs to have an entity ID.

Table 4 below lists exemplary attributes that may be used for defining acharging rule. Note that the “ID” listed here may be a unique ID, suchas a numeric ID, or a uniquely addressable URI that points to theassociated resource.

TABLE 4 Exemplary Attributes for Defining a Charging RuleAttribute/child resource Description ruleID 1106 This is the unique IDof the charging rule. It is created by the CSE when the charging ruleresource is first created. originatorID 1108 This is the unique ID ofthe entity that charges another entity. For example, it may be anapplication ID or an CSE ID. originatorType 1118 This is the type of theoriginator, such as “application”, “CSE”. creatorID 1110 This is theunique ID of the entity that created the charging rule. For example, itmay be an application ID or an CSE ID. In common cases, the “creator”and the “originator” of the charging rule can be the same entity.creatorType 1112 This is the type of the creator, such as “application”,“CSE”. receiverID 1116 This is the unique ID of the entity that beingcharged. For example, it can be an application ID or an CSE ID, or aresource ID. receiverType 1118 This is the type of the receiver, such as“application”, “CSE”. ruleStatus 1120 This attribute indicates whetherthe rule is “active” or “inactive”, or “information recording only”which means no charging is performed. chargingType 1122 This attributeindicates whether the charging rule applies for ONLINE or OFFLINEcharging. chargingModel 1124 This attribute indicates the chargingmodel, such as “session based charging”, “event based charging”,“service based charging”, “session based charging”, etc. sessionID 1126This attribute indicates the unique service session ID, if thechargingType is “session based charging”. It is mandatory of thechargingModel is session based charging. serviceID 1128 This attributeindicates the unique ID of the service being charged. A service providercan define its own services. It is mandatory if the charging model isservice based charging. chargeableEventID 1130 This attribute refers tothe resource that defines the chargeable event that should be applied tothis charging rule. It is mandatory if the charging model is event basedcharging. chargingRateID 1132 This attributes refers to the chargingrate resource. chargingRecordFormID 1134 This attribute refers to the IDof a specific type of a charging record. The format of this chargingrecord should be used for this charging rule. It is mandatory of thecharging type is offline charging or a combined charging type thatrequires charging records. chargingCredit 1104 This child resourcedefines the allowed credit for online charging.

FIG. 12 is a diagram that illustrates exemplary non-limiting resourcestructure 1200 for <chargingCredit> 1104. Table 5 below lists someexemplary attributes for <chargingCredit> 1104.

TABLE 5 Exemplary Attributes for Charging Credit Attribute/childresource Description creditType 1202 This is the type of the credit,such as a type of currency, data storage. creditUnit 1204 This is theunit of the credit, for example, unit of a type of currency, or unit ofdata storage size. allowedCredit 1206 This is the allowed credit for theentity. creditExceedAllowed This defines whether exceeding credit isallowed 1208 or not. creditExceedRoom If exceeding credit limit isallowed, this attribute 1210 defines the allowed room. reservedCredit1212 This attribute shows the reserved credit. currentCredit 1214 Thisattribute shows the current available credit.

FIG. 13 is a diagram that illustrates an exemplary non-limiting resourcestructure 1300 for a charging configuration. Stored using this structuremay be charging configurations and policies, such as chargeable events,chargeable services, rate, and charging record forms. There may also bea collection for the <chargingConfig> resource 1302 that can be calledchargingConfigs. This collection may be made up of <chargingConfig>resources 1302. Table 6 below lists some exemplary attributes (childresources) for chargingConfigs.

TABLE 6 Definition of Child Resources for Charging Configuration ChildResource Name Description chargeableEvents 1304 This is a collection ofchargeable events. It is mandatory when the charging model is eventbased. The graphical illustration is the same as FIG. 10 forchargingRules and it is not shown. Same for other collections.chargeableServices This is a collection of chargeable services. It is1306 mandatory when the charging model is service based. chargingRates1308 This is a collection of charging rates. serviceProcedures This isthe collection of charging record form. It 1310 is mandatory when thecharging type is offline charging, or it is a combined charging typewhich requires charging records.

FIG. 14 is a diagram that illustrates an exemplary non-limiting resourcestructure 1400 for a <chargeableEvent> 1402. Table 7 below lists someexemplary attributes for a <chargeableEvent>.

TABLE 7 Exemplary Attributes for Chargeable Events AttributeNameDescription eventID 1404 This uniquely identifies the chargeable event.eventType 1406 This attribute indicates the type of the event, such asmeter reading. Timer based, storage based charging. eventStart 1408 Thisattribute indicates the start time of the event. eventEnd 1410 Thisattribute indicates the end time of the event. eventDuration Thisattribute indicates the duration of the event.. If a 1412 duration isprovided, the both the start time and the end time are not required.transactionType This attribute defines the type of the chargeable 1414operation, such as CREATE, RETRIEVE. dataSize 1416 This attributedefines the data size if an event is triggered when the stored dataexceeded a certain size.

One embodiment can be considered as a multi-step process. Step 1 can bethe configuration of what service layer charging types are supported asshown in FIG. 13, such as event based, service based, subscriptionbased. oneM2M currently only supports event based charging.

Step 2 can be to configure the policy for the chargeable events. Eachchargeable event has one instance of the data structure shown in FIG.14. For example, in step 2, an entity can define a chargeable eventbased on “transactionType” as “RETRIEVAL”. For each RETRIEVAL operation,it should trigger a chargeable event, e.g. eventID=001. The entity canalso define another chargeable event based on both the transactionTypeand time period. For example it can define “transactionType=RETRIEVALand eventStart=12 pm and eventEnd=20 pm, eventID=002. So for event 002,the chargeable event only happens when both conditions are met, i.e. thechargeable events only happen for the RETRIEVAL operation between 10 pmand 20 pm. Note that in this data structure, we do not specify who ischarging whom (this is done in Step 3). We only define the policies, sothese policies can be used to define many different scenarios in Step 3.

Step 3 can define the specific scenarios based on the chargeable eventdefined in step 2 using the data structure shown in FIG. 11. Here itdefines who is charging whom. For example, for event 001 defined in step2, an entity can define two scenarios, one for CSE1 charging AE1, usingevent 001, and one is for AE1 charging AE2 using event 001. Then forevent 002, it can have a set of specific scenarios, for example, CSE1charging AE1 using event 001, AE2 charging AE1 using event 002. In adeployment there can be many of these scenarios defined based on thepolicies set in step 2.

FIG. 15 is a diagram that illustrates an exemplary non-limiting resourcestructure 1500 for a <chargeableService> 1502. Table 8 below lists someexemplary attributes for a <chargeableService>.

TABLE 8 Exemplary Attributes for Chargeable Services AttributeNameDescription serviceID 1504 This is a unique ID to identify this service.It may be the same ID used in the <chargingRule> resource. Serviceype1506 This defines the service type. The service types may be defined bythe service provider. ServiceDescription 1508 This is the text todescribe the service. serviceProcedures 1510 Defines a collection ofoperations and CSFs involved in order to provide certain services.

FIG. 16 is a diagram that illustrates an exemplary non-limiting resourcestructure 1600 for a <serviceProcedure> 1602. In an embodiment, a<serviceProcedure> resource 1602 may specify the actions needed tofulfill a service. Note that a service request originator may not beable to define the service procedures. The service procedures may bedefined by the CSE, which may determine the entities that are to beinvolved in providing the service. Table 9 below lists some exemplaryattributes for a <serviceProcedure> 1602.

TABLE 9 Exemplary Attributes for Service Procedures AttributeNameDescription seqNum 1609 This is the execution sequence if, for one<chargeableService>, there are more than one <serviceProcedure>.originatorEntityID This indicates the unique ID of the originator of the1606 transaction, such as an CSE ID or an application ID. targetEntityID1608 This indicates the unique ID of the targeted entity by thetransaction. targetResource 1610 This is the URI of the targetedresource for this operation. Transaction 1612 This defines the operationto be performed. <instance> The operation may involve creation/update ofexisting resources so the request will include the data representation.

A chargingRate collection resource may define the rate to be charged fora chargeable event or service. The service provider may choose to postthe rate to the service entities. The chargingRate resource mayassociate a specific chargeable event, a subscriber, a service, etc.with the rate. The rate may be specific to other factors, such as aspecific time. The rate may be dynamically increased or decreased basedon the previous transactions.

ChargingRecords may be created based on the defined<chargingRecordForm>. Each <chargingRecordForm> may define a specificcharging record format. ChargingRecords may be the instances created.

FIG. 17 is a diagram that illustrates a service domain charging system(SD-CS) 1702 that interface, with an underlying 3GPP network via the Zreference point. The anchor point in SD-CS 1702 for Z reference point isthe SD-CM function. In terms of charging related operations, the Zreference point may be realized in different ways, including via theTsp, Gi/SGi and Rx reference points as shown in exemplary, non-limitingarchitecture 1700 of FIG. 17. Tsp is the control plane interface betweenthe SCS 1706 (service domain) and the MTC-IWF 1704. Gi/SGi is the userplane interface between the SCS 1706 and the PGW 1708. Rx is theinterface between the Application Function (AF) and PCRF 1710. 3GPPspecifies that the AF may be a third party application server.

In more de-coupled embodiments, the service domain and 3GPP domain mayexchange CDRs, integrate the CDRs, and regenerate converged billinginformation. In more integrated embodiments, the service domain and the3GPP domain may exchange charging policy information and conductcharging in one domain. Below are listed some of the scenarios involvingSD-CS 1702 interworking with the 3GPP charging and billing system:

-   -   1. 3GPP charging only: SD-CTF collects SD chargeable events and        passes the events to the 3GPP charging system.    -   2. 3GPP assisted charging: SD-CTF collects SD chargeable events;        SD-OFCS generates CDRs and passes the CDRs to the 3GPP charging        system. The 3GPP charging system consolidates the SD-CDRs into        the 3GPP CDRs.    -   3. 3GPP assisted billing: SD-CTF collects SD chargeable events;        SD-OFCS generates CDRs and creates CDR files. SD-CDR files are        transferred from the SD-CS function to the 3GPP MTC-IWF 1704 via        the Tsp reference point. The 3GPP charging system consolidates        the SD-CDR files and the 3GPP CDR files and passes them to the        3GPP billing domain.    -   4. SD independent billing: The SD uses its independent billing        system to process the SD-CDR files. The SD billing system may        exchange information with the 3GPP billing domain.    -   5. SD only billing: The SD gets charging information from the        3GPP charging system and generates converged billing for both        the 3GPP domain and service domain.

The presently disclosed embodiments are related to the service domainand impact to the 3GPP domain is described only as necessary. Note thatsome operations disclosed herein may be performed on more than onereference point. An exemplary list of messages and their applicabilityto different reference points is provided above in Table 3.

Some embodiments utilize the Tsp interface. In such embodiments, theservice domain and the 3GPP domain may exchange charging information.The charging information may be carried in the form of CDRs or CDR filesover the Tsp reference point defined in 3GPP. Such scenarios mayinclude:

-   -   1. MTC-IWF 1704 pulls service domain charging information from        SD-CS 1702    -   2. MTC-IWF 1704 pushes 3GPP domain charging information to SD-CS        1702    -   3. SD-CS 1702 pulls 3GPP domain charging information from        MTC-IWF 1704    -   4. SD-CS 1702 pushes service domain charging information to        MTC-IWF 1704

When an exchange is initiated by SCS 1706, if it is a push, the SD-CS1702 may include the SD-CDR files in the payload of the CDR Transfer Reqmessage. The 3GPP MTC-IWF 1704 may simply respond to the request or itmay also include 3GPP CDR files in the response message. Similaroperations may be used in the other direction when 3GPP initiated theexchange. The service domain and 3GPP domain may also exchange chargingrelated policies via Tsp.

Some embodiments utilize the Rx interface. In such embodiments, the Rxreference point may be used for the service domain and the 3GPP domainto exchange charging related policies. The SCS 1706 may subscribe tonotifications about 3GPP traffic events. For example, the SCS 1706 mayreceive a notification that an IP session has been closed or a UE hashanded over to a different access technology, and the CSE at the SCS1706 may take actions to trigger service domain operations. The servicedomain and the 3GPP domain may exchange session related information overRx for session based charging.

Some embodiments utilize the Gi/SGi interface. In such embodiments,because the service domain operations are user plane traffic in 3GPP,the service domain may include service domain charging informationtogether with the service domain operations (such as data creation,retrieval) and send the information to the 3GPP domain via Gi/SGi. ThePolicy and Charging Enforcement Function (PCEF) 1714 may process theinformation and perform charging at 3GPP.

FIGS. 18A and 18B are a flow chart that illustrates an exemplary signalflow 1800 showing a scenario for SCS initiated device triggering. Insuch embodiments, that service domain may be interworking with 3GPP oncharging related operations. The lines in bold in FIG. 18 indicateoperations and messages in 3GPP. At step 1, a network application 1802may send a request to retrieve data from a MTC device. At step 2, uponreceiving the request, the CSE in the infrastructure node (known as SCS1804 in 3GPP) checks whether the CSE in an end node (MTC) 1806, isregistered, and its online status. In the illustrated signal flow, theMTC 1806 is offline. The SCS determines to trigger the device. Steps 3-9describe the 3GPP procedure to trigger the MTC device 1806. At steps10-12, the MTC device 1806 is online and the status is updated at theinfrastructure node. At steps 13-17, the SD-CTF captures the chargingevent and sends the Charging Report message to the SD-CS 1808. Since theSD-CS 1808 receives the charging event from all CSFs, it may integratethese SD-CDRs and generate the SD-CDR file. The 3GPP and service domainneed to correlate the IMSI and the service domain ID (such assubscription ID) to associate the CDRs in both domains for the same MTCdevice 1806. At steps 18-19, the service domain and 3GPP domain mayexchange CDRs or CDR files over the Tsp reference point. At steps 20-21,at any point when the MTC 1806 is back online, the data retrievalrequest from the network application may be performed and a servicedomain specific SD-CDR may be generated for this operation. This CDR mayor may not be exchanged with the 3GPP charging system.

FIGS. 19A and 19B are a flow chart that illustrates an exemplary signalflow 1900 showing the interactions between SD-CS 1902 and the 3GPPcharging system. The procedures shown in this figure, and the proceduresshown in any figure described herein, do not have to happen in thesequence shown in the respective figure. Such interactions may providemore integrated charging between 3GPP and the service domain.

At steps 1-4, in an embodiment, the 3GPP charging system may be incontrol of SD-CS 1902. The 3GPP charging policy entity PCRF 1904 maysend a charging policy configuration for SD-CS 1902 via the Rx referencepoint. The SD-CS 1902 may configure its charging policy based on inputfrom the 3GPP charging system. At steps 5-8, the MTC-IWF 1906 may send3GPP charging information to the SD-CS 1902 via the Tsp reference point.For example, the MTC-IWF 1906 may have 3GPP subscriber information andthe SD-CS 1902 may associate the 3GPP ID with the service domain IDs. Atsteps 9-12, the PCRF 1904 may pass 3GPP charging related information toSD-CS 1902, such as session status. The SD-CS 1902 may take actionsaccording to its policies. For example, SD-CS 1902 may apply a differentrate when a 3GPP session has been handed over to another accesstechnology. At steps 13-15, in some embodiments, the SD-CS 1902 mayattach service domain charging information in the service domainoperation messages over the user plane reference point Gi/SGi to PCEF1908. Charging may be performed at the PCEF 1908 and the information maybe sent back to SD-CS 1902 over the user plane.

Table 10 below lists exemplary messages related to charging that may beexchanged between the 3GPP domain and the service domain.

TABLE 10 Exemplary Messages Exchanged between 3GPP Domain and ServiceDomain Message Name Descriptions Key IEs Reference Point CDR TransferReq/Rsp The pair of messages is IDs to identify both Tsp used forexchanging 3GPP and service SD-CDRs and 3GPP domain entities and domainCDRs. CDRs associate them can be in the form of together, such as SCSsingle, group or CDR ID, IMSI, 3GPP session files. ID, SD session ID, SDsubscriber ID, 3GPP service flow ID, etc. CDRs Charging Policy The pairof messages is IDs (as above) Rx, Tsp Req/Rsp used for the SD andcharging policies, such 3GPP domain to as charging types, rate, exchangecharging events, etc. policies. One domain can take the dominant role toconfigure the charging policies of another domain. Charging Info Req/RspThe pair of messages is IDs (as above) Rx, Tsp used for the SD andtransaction and traffic 3GPP domain to information that is exchangecharging related to charging related information, such as IDs, sessionstatus, etc. Any service domain Include service domain service domainGi/SGi messages charging information in operations (e.g. data theservice domain retrieval) messages and send service domain or thesemessages over 3GPP domain charging the user plane of 3GPP information(e.g. IDs, charging event, rate, etc.)

FIG. 20 is a diagram that illustrates an exemplary, non-limitingarchitecture 2000 where the SD-CS resides in the Compensation Brokerage(CB) service capability. The figure shows a network case. For devicesand gateways the service capability layer may not contain a SD-CS or theservice capability layer may contain a sub-set of SD-CS. The GatewayCompensation Brokerage (GCB) and Device Compensation Brokerage (DCB) mayonly contain SD-CTF, or SD-CTF and SD-CM. FIG. 21 illustrates exemplary,non-limiting architecture 2100 showing the SD-CS in different nodes.

Table 11 below lists exemplary non-limiting potential charging eventsthat may be supported by an ETSI M2M charging system according to oneembodiment.

TABLE 11 Exemplary ETSI M2M Charging Events ChargeableEntities/Events/Operations Description Key IE Subscription Charging isbased on each M2M Subscription M2M service layer Identifier(subscriber's subscription. profile, contract status, etc.) ETSI M2Mservice connection Charge subscribers per Service connection ID ETSIsecure service (duration of connection, connection. One Service classgranted, subscriber can have etc.) multiple service connections. ETSIM2M SCL NSCL charges subscribers D/G SCL ID (duration of for each D/GSCL. When SCL, allocated D/G SCL registers to space/memory, frequencyNSCL, it triggers a of transactions, etc.) charging event at NSCL ETSIM2M Application NA registers to NSCL; Application ID (duration of DA/GAregisters to D/G Application, allocated SCL; space/memory, frequencyDA/NA is charged for data of transactions, QoS storage services (e.g.granted, etc.) number of containers, . . . ); DA/NA is charged for re-targeting services (number of requests SCL re-targets to anapplication); DA/NA is charged for resource discovery service on SCL;DA/NA is charged for SCL device management or announcement services.ETSI M2M RESTful operations N (D/G) SCL logs the Transaction ID(duration transactions and decides of Transaction, allocated when totrigger a charging space/memory, etc) event based on its charging policyETSI M2M CRUD Reading a resource NSCL charges NA for Resource ID, NA IDoperations example for reading a sensed value. Different data might havedifferent rates depending on NA Creating a resource NSCL charges NA forResource ID, NA ID example for amount of storage NA needs Updating aresource NCSL charges NA for Resource ID, NA ID updating alreadypurchased storage Deleting a resource NSCL charges NA for Resource ID,NA ID deleting purchased storage

FIGS. 23A-23C are diagrams that show interfaces that can be used withembodiments of the service domain charging system and methods. Theinterfaces can be user interfaces, such as graphical user interfaces,that can be used to display and/or control the operation of embodimentsof the service domain charging system and methods.

FIG. 23A is a diagram that shows an exemplary user interface 2302 of oneembodiment that shows chargeable events, such as chargeable event 1 andchargeable event 2 that are associated with a device server or gateway.

FIG. 23B is a diagram that illustrates an exemplary user interface 2304of one embodiment shows chargeable records and associated informationelements.

FIG. 23C is a diagram that illustrates an exemplary user interface 2306of one embodiment that shows API information, such as messages exchangedbetween nodes.

Interfaces, such as interfaces 2302, 2304 and 2306, can be used to viewinformation related to the service domain charging system discussedabove. Interfaces, such as interfaces 2302, 2304 and 2306, can also beused to configure and set data related to the service domain chargingsystem discussed above. For example, such interfaces can be used to setcharging related values for the system.

FIG. 22A is a diagram of an example machine-to machine (M2M), Internetof Things (IoT), or Web of Things (WoT) communication system 10 in whichone or more disclosed embodiments may be implemented. Generally, M2Mtechnologies provide building blocks for the IoT/WoT, and any M2Mdevice, gateway or service platform may be a component of the IoT/WoT aswell as an IoT/WoT service layer, etc. Communication system 10 can beused to implement functionality of the disclosed embodiments and caninclude functionality and logical entities such as Service DomainCharging System, SD-CM 502, SD-OCS 512, SD-OFCS 514, SD-CTF 530, andlogic to produce interfaces, such as interfaces 2302, 2304 and 2306

As shown in FIG. 22A, the M2M/IoT/WoT communication system 10 includes acommunication network 12. The communication network 12 may be a fixednetwork (e.g., Ethernet, Fiber, ISDN, PLC, or the like) or a wirelessnetwork (e.g., WLAN, cellular, or the like) or a network ofheterogeneous networks. For example, the communication network 12 maycomprise of multiple access networks that provides content such asvoice, data, video, messaging, broadcast, or the like to multiple users.For example, the communication network 12 may employ one or more channelaccess methods, such as code division multiple access (CDMA), timedivision multiple access (TDMA), frequency division multiple access(FDMA), orthogonal FDMA (OFDMA), single-carrier FDMA (SC-FDMA), and thelike. Further, the communication network 12 may comprise other networkssuch as a core network, the Internet, a sensor network, an industrialcontrol network, a personal area network, a fused personal network, asatellite network, a home network, or an enterprise network for example.

As shown in FIG. 22A, the M2M/IoT/WoT communication system 10 mayinclude the Infrastructure Domain and the Field Domain. TheInfrastructure Domain refers to the network side of the end-to-end M2Mdeployment, and the Field Domain refers to the area networks, usuallybehind an M2M gateway. The Field Domain includes M2M gateways 14 andterminal devices 18. It will be appreciated that any number of M2Mgateway devices 14 and M2M terminal devices 18 may be included in theM2M/IoT/WoT communication system 10 as desired. Each of the M2M gatewaydevices 14 and M2M terminal devices 18 are configured to transmit andreceive signals via the communication network 12 or direct radio link.The M2M gateway device 14 allows wireless M2M devices (e.g. cellular andnon-cellular) as well as fixed network M2M devices (e.g. PLC) tocommunicate either through operator networks, such as the communicationnetwork 12 or direct radio link. For example, the M2M devices 18 maycollect data and send the data, via the communication network 12 ordirect radio link, to an M2M application 20 or M2M devices 18. The M2Mdevices 18 may also receive data from the M2M application 20 or an M2Mdevice 18. Further, data and signals may be sent to and received fromthe M2M application 20 via an M2M service layer 22, as described below.M2M devices 18 and gateways 14 may communicate via various networksincluding, cellular, WLAN, WPAN (e.g., Zigbee, 6LoWPAN, Bluetooth),direct radio link, and wireline for example.

Referring to FIG. 22B, the illustrated M2M service layer 22 in the fielddomain provides services for the M2M application 20, M2M gateway devices14, and M2M terminal devices 18 and the communication network 12.Communication network 12 can be used to implement functionality of thedisclosed embodiments and can include capillary device chargingfunctionality and logical entities such as such as Service DomainCharging System, SD-CM 502, SD-OCS 512, SD-OFCS 514, SD-CTF 530, andlogic to produce interfaces, such as interfaces 2302, 2304 and 2306. TheM2M service layer 22 may be implemented by one or more servers,computers, devices, virtual machines (e.g. cloud/storage farms, etc.) orthe like, including for example the devices illustrated in FIGS. 22C and22D described below. It will be understood that the M2M service layer 22may communicate with any number of M2M applications, M2M gateway devices14, M2M terminal devices 18 and communication networks 12 as desired.The M2M service layer 22 may be implemented by one or more servers,computers, or the like. The M2M service layer 22 provides servicecapabilities that apply to M2M terminal devices 18, M2M gateway devices14 and M2M applications 20. The functions of the M2M service layer 22may be implemented in a variety of ways, for example as a web server, inthe cellular core network, in the cloud, etc. Similar to the illustratedM2M service layer 22, there is the M2M service layer 22′ in theInfrastructure Domain. M2M service layer 22′ provides services for theM2M application 20′ and the underlying communication network 12′ in theinfrastructure domain. M2M service layer 22′ also provides services forthe M2M gateway devices 14 and M2M terminal devices 18 in the fielddomain. It will be understood that the M2M service layer 22′ maycommunicate with any number of M2M applications, M2M gateway devices andM2M terminal devices. The M2M service layer 22′ may interact with aservice layer by a different service provider. The M2M service layer 22′may be implemented by one or more servers, computers, virtual machines(e.g. cloud/compute/storage farms, etc.) or the like.

Referring also to FIG. 22B, the M2M service layer 22 and 22′ provide acore set of service delivery capabilities that diverse applications andverticals can leverage. These service capabilities enable M2Mapplications 20 and 20′ to interact with devices and perform functionssuch as data collection, data analysis, device management, security,billing, service/device discovery etc. Essentially, these servicecapabilities free the applications of the burden of implementing thesefunctionalities, thus simplifying application development and reducingcost and time to market. The service layer 22 and 22′ also enables M2Mapplications 20 and 20′ to communicate through various networks 12 and12′ in connection with the services that the service layer 22 and 22′provide. The connection methods of the present application may beimplemented as part of a service layer 22 and 22′. The service layer 22and 22′ is a software middleware layer that supports value-added servicecapabilities through a set of Application Programming Interfaces (APIs)and underlying networking interfaces. Both ETSI M2M and oneM2M use aservice layer that may contain the connection methods of the presentapplication. ETSI M2M's service layer is referred to as the ServiceCapability Layer (SCL). The SCL may be implemented within an M2M device(where it is referred to as a device SCL (DSCL)), a gateway (where it isreferred to as a gateway SCL (GSCL)) and/or a network node (where it isreferred to as a network SCL (NSCL)). The oneM2M service layer supportsa set of Common Service Functions (CSFs) (i.e. service capabilities). Aninstantiation of a set of one or more particular types of CSFs isreferred to as a Common Services Entity (CSE) which can be hosted ondifferent types of network nodes (e.g. infrastructure node, middle node,application-specific node). Further, connection methods of the presentapplication can implemented as part of an M2M network that uses aService Oriented Architecture (SOA) and/or a resource-orientedarchitecture (ROA) to access services such as the connection methods ofthe present application.

In some embodiments, M2M applications 20 and 20′ may include theapplications that interact with capillary devices and therefore may beused in conjunction with the disclosed systems and methods for capillarydevice charging. The M2M applications 20 and 20′ may include theapplications that interact with the UE or gateway and may also be usedin conjunction with other disclosed charging systems and methods. TheM2M applications 20 and 20′ may include applications in variousindustries such as, without limitation, transportation, health andwellness, connected home, energy management, asset tracking, andsecurity and surveillance. As mentioned above, the M2M service layer,running across the devices, gateways, and other servers of the system,supports functions such as, for example, data collection, devicemanagement, security, billing, location tracking/geofencing,device/service discovery, and legacy systems integration, and providesthese functions as services to the M2M applications 20 and 20′.

Generally, the service layers 22 and 22′ define a software middlewarelayer that supports value-added service capabilities through a set ofApplication Programming Interfaces (APIs) and underlying networkinginterfaces. Both the ETSI M2M and oneM2M architectures define a servicelayer. ETSI M2M's service layer is referred to as the Service CapabilityLayer (SCL). The SCL may be implemented within an M2M device (where itis referred to as a device SCL (DSCL)), a gateway (where it is referredto as a gateway SCL (GSCL)) and/or a network node (where it is referredto as a network SCL (NSCL)). The oneM2M service layer supports a set ofCommon Service Functions (CSFs) (i.e. service capabilities). Aninstantiation of a set of one or more particular types of CSFs isreferred to as a Common Services Entity (CSE) which can be hosted ondifferent types of network nodes (e.g. infrastructure node, middle node,application-specific node). The Third Generation Partnership Project(3GPP) has also defined an architecture for machine-type communications(MTC). In that architecture, the service layer, and the servicecapabilities is provides, are implemented as part of a ServiceCapability Server (SCS). Whether embodied in a DSCL, GSCL, or NSCL ofthe ETSI M2M architecture, in a Service Capability Server (SCS) of the3GPP MTC architecture, in a CSF or CSE of the oneM2M architecture, or assome other component or module of a network, the service layer may beimplemented as a logical entity (e.g., software, computer-executableinstructions, and the like) executing either on one or more standaloneservers, computers, or other computing devices or nodes in the networkor as part of one or more existing servers, computers, or nodes of suchnetwork. As an example, a service layer or component thereof may beimplemented in the form of software running on a server, computer, ordevice having the general architecture illustrated in FIG. 22C or FIG.22D described below.

Further, the logical entities of the present application such as ServiceDomain Charging System, SD-CM 502, SD-OCS 512, SD-OFCS 514, SD-CTF 530,and logic to produce interfaces, such as interfaces 2302, 2304 and 2306can implemented as part of an M2M network that uses a Service OrientedArchitecture (SOA) and/or a resource-oriented architecture (ROA) toaccess services of the present application.

FIG. --C is a system diagram of an example device 30, that can be an M2Mdevice, user equipment, gateway, UE/GW or any other nodes includingnodes of the mobile care network, service layer network applicationprovider, terminal device 18 or an M2M gateway device 14 for example.The device 30 can execute or include logical entities such as such asService Domain Charging System, SD-CM 502, SD-OCS 512, SD-OFCS 514,SD-CTF 530, and logic to produce interfaces, such as interfaces 2302,2304 and 2306. The device 30 can be part of an M2M network as shown inFIG. 22A-B or part of a non-M2M network. As shown in FIG. 22C, thedevice 30 may include a processor 32, a transceiver 34, atransmit/receive element 36, a speaker/microphone 38, a keypad 40, adisplay/touchpad/indicator(s) 42, non-removable memory 44, removablememory 46, a power source 48, a global positioning system (GPS) chipset50, and other peripherals 52. It will be appreciated that the device 30may include any sub-combination of the foregoing elements whileremaining consistent with an embodiment. This device may be a devicethat uses and/or implements the disclosed systems and methods forcapillary device charging or other disclosed charging systems andmethods.

The processor 32 may be a general purpose processor, a special purposeprocessor, a conventional processor, a digital signal processor (DSP), aplurality of microprocessors, one or more microprocessors in associationwith a DSP core, a controller, a microcontroller, one or moreApplication Specific Integrated Circuits (ASICs), one or more FieldProgrammable Gate Array (FPGAs) circuits, any other type and number ofintegrated circuits (ICs), a state machine, and the like. The processor32 may perform signal coding, data processing, power control,input/output processing, and/or any other functionality that enables thedevice 30 to operate in a wireless environment. The processor 32 may becoupled to the transceiver 34, which may be coupled to thetransmit/receive element 36. While FIG. 22C depicts the processor 32 andthe transceiver 34 as separate components, it will be appreciated thatthe processor 32 and the transceiver 34 may be integrated together in anelectronic package or chip. The processor 32 may performapplication-layer programs (e.g., browsers) and/or radio access-layer(RAN) programs and/or communications. The processor 32 may performsecurity operations such as authentication, security key agreement,and/or cryptographic operations, such as at the access-layer and/orapplication layer for example.

The transmit/receive element 36 may be configured to transmit signalsto, and/or receive signals from, an M2M service platform 22. Forexample, in an embodiment, the transmit/receive element 36 may be anantenna configured to transmit and/or receive RF signals. Thetransmit/receive element 36 may support various networks and airinterfaces, such as WLAN, WPAN, cellular, and the like. In anembodiment, the transmit/receive element 36 may be an emitter/detectorconfigured to transmit and/or receive IR, UV, or visible light signals,for example. In yet another embodiment, the transmit/receive element 36may be configured to transmit and receive both RF and light signals. Itwill be appreciated that the transmit/receive element 36 may beconfigured to transmit and/or receive any combination of wireless orwired signals.

In addition, although the transmit/receive element 36 is depicted inFIG. 22C as a single element, the device 30 may include any number oftransmit/receive elements 36. More specifically, the device 30 mayemploy MIMO technology. Thus, in an embodiment, the device 30 mayinclude two or more transmit/receive elements 36 (e.g., multipleantennas) for transmitting and receiving wireless signals.

The transceiver 34 may be configured to modulate the signals that are tobe transmitted by the transmit/receive element 36 and to demodulate thesignals that are received by the transmit/receive element 36. As notedabove, the device 30 may have multi-mode capabilities. Thus, thetransceiver 34 may include multiple transceivers for enabling device 30to communicate via multiple RATs, such as UTRA and IEEE 802.11, forexample.

The processor 32 may access information from, and store data in, anytype of suitable memory, such as the non-removable memory 44 and/or theremovable memory 46. The non-removable memory 44 may includerandom-access memory (RAM), read-only memory (ROM), a hard disk, or anyother type of memory storage device. The removable memory 46 may includea subscriber identity module (SIM) card, a memory stick, a securedigital (SD) memory card, and the like. In other embodiments, theprocessor 32 may access information from, and store data in, memory thatis not physically located on the device 30, such as on a server or ahome computer.

The processor 30 may receive power from the power source 48, and may beconfigured to distribute and/or control the power to the othercomponents in the device 30. The power source 48 may be any suitabledevice for powering the device 30. For example, the power source 48 mayinclude one or more dry cell batteries (e.g., nickel-cadmium (NiCd),nickel-zinc (NiZn), nickel metal hydride (NiMH), lithium-ion (Li-ion),etc.), solar cells, fuel cells, and the like.

The processor 32 may also be coupled to the GPS chipset 50, which may beconfigured to provide location information (e.g., longitude andlatitude) regarding the current location of the device 30. It will beappreciated that the device 30 may acquire location information by wayof any suitable location-determination method while remaining consistentwith an embodiment.

The processor 32 may further be coupled to other peripherals 52, whichmay include one or more software and/or hardware modules that provideadditional features, functionality and/or wired or wirelessconnectivity. For example, the peripherals 52 may include anaccelerometer, an e-compass, a satellite transceiver, a sensor, adigital camera (for photographs or video), a universal serial bus (USB)port, a vibration device, a television transceiver, a hands freeheadset, a Bluetooth® module, a frequency modulated (FM) radio unit, adigital music player, a media player, a video game player module, anInternet browser, and the like.

FIG. 22D is a block diagram of an exemplary computing system 90 onwhich, for example, the M2M service platform 22 of FIGS. 22A and 22B maybe implemented. Computing system 90 may comprise a computer or serverand may be controlled primarily by computer readable instructions, whichmay be in the form of software, wherever, or by whatever means suchsoftware is stored or accessed. Computing system 90 can execute orinclude logical entities such as Service Domain Charging System, SD-CM502, SD-OCS 512, SD-OFCS 514, SD-CTF 530, and logic to produceinterfaces, such as interfaces 2302, 2304 and 2306. Computing system 90can be an M2M device, user equipment, gateway, UE/GW or any other nodesincluding nodes of the mobile care network, service layer networkapplication provider, terminal device 18 or an M2M gateway device 14 forexample. Such computer readable instructions may be executed withincentral processing unit (CPU) 91 to cause computing system 90 to dowork. In many known workstations, servers, and personal computers,central processing unit 91 is implemented by a single-chip CPU called amicroprocessor. In other machines, the central processing unit 91 maycomprise multiple processors. Coprocessor 81 is an optional processor,distinct from main CPU 91 that performs additional functions or assistsCPU 91. CPU 91 and/or coprocessor 81 may receive, generate, and processthe data used in various embodiments of the disclosed systems andmethods for capillary device charging or other disclosed chargingsystems and methods.

In operation, CPU 91 fetches, decodes, and executes instructions, andtransfers information to and from other resources via the computer'smain data-transfer path, system bus 80. Such a system bus connects thecomponents in computing system 90 and defines the medium for dataexchange. System bus 80 typically includes data lines for sending data,address lines for sending addresses, and control lines for sendinginterrupts and for operating the system bus. An example of such a systembus 80 is the PCI (Peripheral Component Interconnect) bus.

Memory devices coupled to system bus 80 include random access memory(RAM) 82 and read only memory (ROM) 93. Such memories include circuitrythat allows information to be stored and retrieved. ROMs 93 generallycontain stored data that cannot easily be modified. Data stored in RAM82 may be read or changed by CPU 91 or other hardware devices. Access toRAM 82 and/or ROM 93 may be controlled by memory controller 92. Memorycontroller 92 may provide an address translation function thattranslates virtual addresses into physical addresses as instructions areexecuted. Memory controller 92 may also provide a memory protectionfunction that isolates processes within the system and isolates systemprocesses from user processes. Thus, a program running in a first modecan access only memory mapped by its own process virtual address space;it cannot access memory within another process's virtual address spaceunless memory sharing between the processes has been set up.

In addition, computing system 90 may contain peripherals controller 83responsible for communicating instructions from CPU 91 to peripherals,such as printer 94, keyboard 84, mouse 95, and disk drive 85. Display86, which is controlled by display controller 96, is used to displayvisual output generated by computing system 90. Such visual output mayinclude text, graphics, animated graphics, and video. Display 86 may beimplemented with a CRT-based video display, an LCD-based flat-paneldisplay, gas plasma-based flat-panel display, or a touch-panel. Displaycontroller 96 includes electronic components required to generate avideo signal that is sent to display 86.

Further, computing system 90 may contain network adaptor 97 that may beused to connect computing system 90 to an external communicationsnetwork, such as network 12 of FIGS. 22A and 22B. In an embodiment,network adaptor 97 may receive and transmit data used by variousdisclosed systems and methods for capillary device charging or otherdisclosed charging systems and methods.

It is understood that any or all of the systems, methods, and processesdescribed herein may be embodied in the form of computer executableinstructions (i.e., program code) stored on a computer-readable storagemedium. Such instructions, when executed by a machine, such as acomputer, server, M2M terminal device, M2M gateway device, or the like,perform and/or implement the systems, methods and processes describedherein. Specifically, any of the steps, operations or functionsdescribed above, including the operations of the gateway, UE, UE/GW, orany of the nodes of the mobile core network, service layer or networkapplication provider, may be implemented in the form of such computerexecutable instructions. Logical entities s such as Service DomainCharging System, SD-CM 502, SD-OCS 512, SD-OFCS 514, SD-CTF 530, andlogic to produce interfaces, such as interfaces 2302, 2304 and 2306 maybe embodied in the form of the computer executable instructions.Computer readable storage media include both volatile and nonvolatile,removable and non-removable media implemented in any method ortechnology for storage of information, but such computer readablestorage media do not include signals. Computer readable storage mediainclude, but are not limited to, RAM, ROM, EEPROM, flash memory or othermemory technology, CDROM, digital versatile disks (DVD) or other opticaldisk storage, magnetic cassettes, magnetic tape, magnetic disk storageor other magnetic storage devices, or any other physical medium that canbe used to store the desired information and that can be accessed by acomputer.

In describing preferred embodiments of the subject matter of the presentdisclosure, as illustrated in the FIGS., specific terminology isemployed for the sake of clarity. The claimed subject matter, however,is not intended to be limited to the specific terminology so selected,and it is to be understood that each specific element includes alltechnical equivalents that operate in a similar manner to accomplish asimilar purpose.

This written description uses examples to disclose the invention,including the best mode, and also to enable any person skilled in theart to practice the invention, including making and using any devices orsystems and performing any incorporated methods. The patentable scope ofthe invention is defined by the claims and may include other examplesthat occur to those skilled in the art. Such other examples are intendedto be within the scope of the claims if they have structural elementsthat do not differ from the literal language of the claims, or if theyinclude equivalent structural elements with insubstantial differencesfrom the literal languages of the claims.

What is claimed is:
 1. In a service layer of a communication network, amethod comprising: receiving instructions at the Service Layer from a3GPP network function, where the instructions are used by the ServiceLayer to configure charging policies within a Service Domain ChargingFunction, the charging policies containing charging rules; receivingcharging information from an underlying 3GPP network function, where thecharging information includes a 3GPP external identifier, 3GPPsubscriber information and/or 3GPP session status; correlating, based onthe configured policies and the charging information, the 3GPP externalidentifier with a Service Layer identifier; and creating, based on thecorrelating step, a charging data record including the 3GPP externalidentifier and the Service Layer identifier.
 2. The method of claim 1further comprising: sending the charging record to a 3GPP networkfunction.
 3. The method of claim 2, wherein a different rate is incurredwhen a 3GPP session is handed off to a different access networktechnology.
 4. The method of claim 1, wherein the 3GPP identifier is anIMSI.
 5. The method of claim 1, wherein the Service Layer identifier isa Service Subscription ID.
 6. The method of claim 1, wherein thereceived instructions are from a 3GPP PCRF function.
 7. The method ofclaim 1, wherein the received charging information is from a 3GPPMTC-IWF function.
 8. A system comprising: a non-transitory memoryincluding instructions for configuring charging policies in acommunication network; and a processor operably coupled to thenon-transitory memory configured to execute the instructions of:receiving instructions at a Service Layer from a 3GPP network function,where the instructions are used by the Service Layer to configurecharging policies within a Service Domain Charging Function; receivingcharging information from an underlying 3GPP network function, where thecharging information includes one or more of a 3GPP external identifier,3GPP subscriber information and 3GPP session status; correlating, basedon the configured charging policies and the charging information, the3GPP external identifier with a Service Layer identifier; and creating,based on the correlating step, a charging data record including the 3GPPexternal identifier and the Service Layer identifier.
 9. The system ofclaim 8, further comprising: sending the charging record to a 3GPPnetwork function.
 10. The system of claim 9, wherein a different rate ischarged when a 3GPP session is handed off to a different access networktechnology.
 11. The system of claim 8, wherein the 3GPP identifier is anIMSI.
 12. The system of claim 8, wherein the Service Layer externalidentifier is a Service Subscription ID.
 13. The system of claim 8,wherein the received instructions are from a 3GPP PCRF function.
 14. Thesystem of claim 8, wherein the received charging information is from a3GPP MTC-IWF function.
 15. The system of claim 14, wherein the chargingpolicies contain charging rules.
 16. The system of claim 15, wherein thecharging policies define service based charging.
 17. The system of claim15, wherein the charging policies include an eventID attributeidentifying an event.
 18. The system of claim 17, wherein the chargingpolicies include an eventType attribute indicating a type of event. 19.The system of claim 15, wherein the charging policies include anoperationType attribute defining a type of operation to be collected.20. The system of claim 15, wherein charging policies include achargingCredit attribute defining allowed credit for online charging,and a chargingType attribute indicating whether the charging ruleapplies for ONLINE or OFFLINE charging.